DOC: inconsistent default values in the initialiser for RangeIndex #62901
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
|
Hi, I would like to mention that |
thanks, I added to |
mroeschke
approved these changes
Oct 29, 2025
|
Thanks @natmokval |
zhangbowen-coder
pushed a commit
to zhangbowen-coder/pandas
that referenced
this pull request
Oct 30, 2025
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
RangeIndex#62899Updated the docstring in the initialiser for RangeIndex.
I noticed, if
stepparameter is None, it defaults to 1. We have a similar case inslice_indexerpandas/pandas/core/indexes/base.py
Lines 6637 to 6644 in ce3298b
should we also clarify for
stepparameter:If None, defaults to 1.?